Skip to content

Addendum for Export Refactoring PR - #12594

Draft
poikilotherm wants to merge 8 commits into
IQSS:11405-refactor-exportsfrom
poikilotherm:11405-addendum
Draft

Addendum for Export Refactoring PR#12594
poikilotherm wants to merge 8 commits into
IQSS:11405-refactor-exportsfrom
poikilotherm:11405-addendum

Conversation

@poikilotherm

Copy link
Copy Markdown
Contributor

No description provided.

…istryBean IQSS#11405

- Moved exporter management logic into a dedicated `ExporterRegistryBean` singleton for improved modularity and maintainability.
- Simplified `ExportService` to delegate exporter logic to the new registry.
- Enable injectingthe registry and other components
- The export process itself is stateless. State is involved in potential write locks, the loaded plugins, etc.
- A stateless coordinator bean scales better for multiple export requests coming in.
…alidator, and storage abstraction IQSS#11405

The goal is removing the caching logic from the ExportService. At the same time, a distinct caching subsystem shall have policies about what gets cached, when it expires etc, all independent of a coordinating service like ExportService.

This make cognitive loader smaller and allows extension without using more code branches.
…eIOCache class IQSS#11405

- Reorganized export cache handling into a dedicated `StorageIOCache` service, improving modularity and reducing cognitive load in `ExportService`.
- Streamlined caching operations with a unified approach across all storage drivers.
- Deprecated legacy unversioned cache keys; introduced versioned aux tag schema for better cache qualification.
- Enhanced write atomicity and cache eviction logic.
- Remove stale code for size of exports
…OCache IQSS#11405

The legacy reading of cached exports is prone to produce bugs in production.

When we rely on reading cached exports as prerequisites for other metadata formats, we might end up with stale data. Any export has no knowledge about whether and when an export of another format happened. We keep no provenance per format.

Assuming there is a cached "latest" with the legacy file format, it would be read as a prerequisite format, but our invalidation mechanisms would not be able to tell if it's actually stale, because it was not yet re-exported.

Any released version is immutable, thus if we rely in lookups on cached objects with the version present in the aux tag, we can be sure we get the latest data.
…constructor

- Added null and blank checks for dataset, version, and formatName to ensure robust usage.
- Introduced a convenience constructor for creating cache keys directly from a dataset version and format.
@poikilotherm poikilotherm self-assigned this Aug 7, 2026
…rvice` package and rename `ExportService` to `ExportServiceBean`

- "ExportServiceBean" is more aligned with the codebase style where EJBs mostly have a "Bean" name suffix.
- Also move test classes into the same package (under the test source tree)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant